From ns1.win.net!owner-techknow-l Mon Aug 28 10:56:24 1995 remote from Mailbox Received: by techknow.techknow.com for Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 28 Aug 95 10:56 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 28 Aug 95 10:54 CDT Received: (from majordom@localhost) by ns1.win.net (8.6.11/8.6.9) id KAA06392 for techknow-l-outgoing; Mon, 28 Aug 1995 10:44:14 -0400 Received: (from nobody@localhost) by ns1.win.net (8.6.11/8.6.9) id KAA06354 for ; Mon, 28 Aug 1995 10:44:11 -0400 Received: from dub-img-4.compuserve.com(198.4.9.4) by ns1.win.net via smap (V1.3) id sma006178; Mon Aug 28 10:43:48 1995 Received: by dub-img-4.compuserve.com (8.6.10/5.950515) id KAA09963; Mon, 28 Aug 1995 10:39:05 -0400 Date: 28 Aug 95 10:36:51 EDT From: "Glen E. Fleharty" <74660.555@compuserve.com> To: Excal List Subject: RE: Security Message-ID: <950828143651_74660.555_EHB65-1@CompuServe.COM> Sender: owner-techknow-l@ns1.win.net Precedence: bulk Reply-To: techknow-l@ns1.win.net REPLY-TO: techknow-l@ns1.win.net ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ origin : windows techknow(tm)list sender : "Glen E. Fleharty" <74660.555@compuserve.com> ---------------------------------- I had to do some searching of my archives, but I found a document called FLAGS.WRI that may explain better the security changes found in .95. The following is an excerpt from this document if you would like a copy send me a private E-mail, or if you're lucky enough to get through to HQ you can get it there. Flag Grouping For convenience, it is possible to group collections of flags. Flag groupings are done with one of the following: ~and( flag1, flag2 ) Both flags must exist ~or( flag1, flag2 ) Either or both flags must exist ~not( flag ) The flag can't exist You might set a condition in a screen to require that a user have a flag you created called "member" and have a high speed modem to access part of your BBS with: ~and(member,~hispeed) Of if you wish grant access to an area of your BBS only if the user is over 18 or you have, from experience with the younger user, granted him/her a "mature" flag, you can do that with the following: ~or(~adultage,mature) You can nest conditions. The following requires that all four flags be set. ~and( ~and(flag1, flag2), ~and(flag3,flag4)) You can also use comparison flags. The following will check to see if the user has given you a work or home phone: ~or( ~ne(phonehome,""),~ne(phonework,"")) Note: It is best not to wrap the entire condition in the ~not() flag. You can accomplish that by setting the appropriate button in the condition check in Merlin. Glen @ Environet Works Soon to be on-line ---------------------------------- origin : windows techknow(tm)list reply to: techknow-L@lists.win.net sender : "Glen E. Fleharty" <74660.555@compuserve.com>